Hints and Tips

If InfoCourier can't seem to find a graphic or link you are specifying at design time, then try compiling your HTML. The compiled EXE uses a slightly different algorithm for locating other support files at execution time, and you may find that it successfully locates the graphics/links then. This is usually caused by a conflict in the re-specification of the root directory (i.e. your link starts with a / when it really doesn't need to) We are investigating changing the way this works.
Compiling will be quicker if you don't use the GIF format for graphics if possible. (End user display speed is similar for all image formats, perhaps a little slower for JPEG's, but the size and complexity of the image is the most important factor)
The browser caches graphics, so re-using a graphic repeatedly on the same page or on multiple pages is very quick. (It caches the 20 most recently used graphics).
The browser in a compiled distributable starts with the colors and fonts as they were when you compiled it, and the home page is the page you were on when you compiled.
GPF's at startup on a users machine (very rare) are nearly always video driver related. If your user experiences this problem get them to try switching to a Microsoft Generic (S)VGA video driver (using Windows Setup in Win3.x or in Win95 go Control Panel/System/Device Manager, open the "Display Adapter" tree and select the properties for the adapter).
You can allow the user to print a nice manual by specifying the Print Sequence of each HTML "page" and enabling the "Print All" option in the Compiler Options.
You can prevent a user from extracting information by disabling the "Copy" option in the Compiler Options.
If you have date-sensitive information you can specify a date beyond which the information will not display, again in the Compiler Options.
If the default background color etc. don't seem to be accepted in your compiled distributable it is probably because the pages themselves are defining that attribute, the background color or font etc. The user can override it for a single page, but it will flick back when he jumps elsewhere.